From Windows XP and later, Windows supports a concept called "Registration-Free COM" where an application uses a ".manifest" file to describe the COM components it uses. Then, Windows loads them in an isolated manner without the need for registration, or administrator rights and interference from other versions located in the system.

In our recent releases of Xceed Zip, we've started including .manifest files that describe the component so RegFree COM can be used by customers.

A XceedZip.dll.manifest file is now part of the distribution. It is not useful for development but if you look at the file's contents, you'll see the definition of the COM interface for the component in standard XML format. This will allow Windows to load and bind the component to your application on-the-fly without prior registration or administrator rights.

The manifest file contains a hash value based on the XceedZip.dll file. So if you get a new version of XceedZip, you need to update the manifest file as well.

When you deploy your application:

1. Rename XceedZip.dll.manifest to your executable's filename, e.g.: MyApplication.exe.manifest. If your executable already has a manifest file, you can simply add the contents of the <assembly> node of our manifest to yours.
2. Copy that application manifest file to the same folder as your executable.
3. Do not install XceedZip.dll in the system32 folder anymore. Instead, copy the file in the same folder as your executable.
4. No need to perform regsvr32.exe with XceedZip.dll anymore. As long as the DLL is in the same folder as your executable and the executable's manifest file contains the contents of the XceedZip.dll.manifest, it should work.

Your application should now ignore whatever is registered on the system and/or located in system32 and use the XceedZip.dll file that's located in your executable's folder.